Skip to content

Conversation

LimberHope
Copy link
Collaborator

@LimberHope LimberHope commented Oct 8, 2025

@LimberHope LimberHope marked this pull request as draft October 8, 2025 14:42
@LimberHope LimberHope requested a review from roguenet October 13, 2025 14:09
@LimberHope LimberHope marked this pull request as ready for review October 13, 2025 14:32
@roguenet roguenet changed the base branch from staging to release/precious-pearl October 14, 2025 16:13
entries: DisturbanceReportEntryDto[] | null;

@ApiProperty({ type: Number })
disturbanceableId: number;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two things:

  • Shouldn't this be nullable? If I remember correctly, we've made this field nullable because of the change in how we're relating disturbances.
  • This field is kind of meaningless without the type as well. Even if you don't think you need it for your current ticket, it should be included.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

resolved

@LimberHope LimberHope requested a review from roguenet October 14, 2025 18:28
@LimberHope LimberHope merged commit b3b9826 into release/precious-pearl Oct 14, 2025
1 check passed
@LimberHope LimberHope deleted the TM-2517-enable-the-approval-flow-of-disturbance-reports branch October 14, 2025 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants